% LaTeX Template f�r Seminar "Wissenschaftliches Arbeiten" 182.697
% Uses IEEEtran style, adapted from bare_conf.tex
%
% v0.1  U. Schmid  26.9.2014    Initial version

% Ein paar n�tzliche Makros

\newcommand{\zitat}[1]{\lqq \emph{#1}\rqq}
\newcommand{\lqq}{\lq\lq}
\newcommand{\rqq}{\rq\rq}

%% bare_conf.tex
%% V1.3
%% 2007/01/11
%% by Michael Shell
%% See:
%% http://www.michaelshell.org/
%% for current contact information.
%%
%% This is a skeleton file demonstrating the use of IEEEtran.cls
%% (requires IEEEtran.cls version 1.7 or later) with an IEEE conference paper.
%%
%% Support sites:
%% http://www.michaelshell.org/tex/ieeetran/
%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/
%% and
%% http://www.ieee.org/

%%*************************************************************************
%% Legal Notice:
%% This code is offered as-is without any warranty either expressed or
%% implied; without even the implied warranty of MERCHANTABILITY or
%% FITNESS FOR A PARTICULAR PURPOSE! 
%% User assumes all risk.
%% In no event shall IEEE or any contributor to this code be liable for
%% any damages or losses, including, but not limited to, incidental,
%% consequential, or any other damages, resulting from the use or misuse
%% of any information contained here.
%%
%% All comments are the opinions of their respective authors and are not
%% necessarily endorsed by the IEEE.
%%
%% This work is distributed under the LaTeX Project Public License (LPPL)
%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used,
%% distributed and modified. A copy of the LPPL, version 1.3, is included
%% in the base LaTeX documentation of all distributions of LaTeX released
%% 2003/12/01 or later.
%% Retain all contribution notices and credits.
%% ** Modified files should be clearly indicated as such, including  **
%% ** renaming them and changing author support contact information. **
%%
%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex,
%%                    bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex
%%*************************************************************************

% *** Authors should verify (and, if needed, correct) their LaTeX system  ***
% *** with the testflow diagnostic prior to trusting their LaTeX platform ***
% *** with production work. IEEE's font choices can trigger bugs that do  ***
% *** not appear when using other class files.                            ***
% The testflow support page is at:
% http://www.michaelshell.org/tex/testflow/

% Note that the a4paper option is mainly intended so that authors in
% countries using A4 can easily print to A4 and see how their papers will
% look in print - the typesetting of the document will not typically be
% affected with changes in paper size (but the bottom and side margins will).
% Use the testflow package mentioned above to verify correct handling of
% both paper sizes by the user's LaTeX system.
%
% Also note that the "draftcls" or "draftclsnofoot", not "draft", option
% should be used if it is desired that the figures are to be displayed in
% draft mode.
%
\documentclass[conference,A4]{IEEEtran}
% Add the compsoc option for Computer Society conferences.
%
% If IEEEtran.cls has not been installed into the LaTeX system files,
% manually specify the path to it like:
% \documentclass[conference]{../sty/IEEEtran}

% Some very useful LaTeX packages include:
% (uncomment the ones you want to load)

% *** MISC UTILITY PACKAGES ***
%
%\usepackage{ifpdf}
% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional
% compilation based on whether the output is pdf or dvi.
% usage:
% \ifpdf
%   % pdf code
% \else
%   % dvi code
% \fi
% The latest version of ifpdf.sty can be obtained from:
% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/
% Also, note that IEEEtran.cls V1.7 and later provides a builtin
% \ifCLASSINFOpdf conditional that works the same way.
% When switching from latex to pdflatex and vice-versa, the compiler may
% have to be run twice to clear warning/error messages.

% *** CITATION PACKAGES ***
%
%\usepackage{cite}
% cite.sty was written by Donald Arseneau
% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package
% \cite{} output to follow that of IEEE. Loading the cite package will
% result in citation numbers being automatically sorted and properly
% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using
% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's
% \cite will automatically add leading space, if needed. Use cite.sty's
% noadjust option (cite.sty V3.8 and later) if you want to turn this off.
% cite.sty is already installed on most LaTeX systems. Be sure and use
% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does
% not currently provide for hyperlinked citations.
% The latest version can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/
% The documentation is contained in the cite.sty file itself.

% *** GRAPHICS RELATED PACKAGES ***
%
\ifCLASSINFOpdf
  \usepackage[pdftex]{graphicx}
  % declare the path(s) where your graphic files are
  % \graphicspath{{../pdf/}{../jpeg/}}
  % and their extensions so you won't have to specify these with
  % every instance of \includegraphics
  % \DeclareGraphicsExtensions{.pdf,.jpeg,.png}
\else
  % or other class option (dvipsone, dvipdf, if not using dvips). graphicx
  % will default to the driver specified in the system graphics.cfg if no
  % driver is specified.
  % \usepackage[dvips]{graphicx}
  % declare the path(s) where your graphic files are
  % \graphicspath{{../eps/}}
  % and their extensions so you won't have to specify these with
  % every instance of \includegraphics
  % \DeclareGraphicsExtensions{.eps}
\fi
% graphicx was written by David Carlisle and Sebastian Rahtz. It is
% required if you want graphics, photos, etc. graphicx.sty is already
% installed on most LaTeX systems. The latest version and documentation can
% be obtained at: 
% http://www.ctan.org/tex-archive/macros/latex/required/graphics/
% Another good source of documentation is "Using Imported Graphics in
% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or
% epslatex.pdf at: http://www.ctan.org/tex-archive/info/
%
% latex, and pdflatex in dvi mode, support graphics in encapsulated
% postscript (.eps) format. pdflatex in pdf mode supports graphics
% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure
% that all non-photo figures use a vector format (.eps, .pdf, .mps) and
% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats
% which can result in "jaggedy"/blurry rendering of lines and letters as
% well as large increases in file sizes.
%
% You can find documentation about the pdfTeX application at:
% http://www.tug.org/applications/pdftex

% *** MATH PACKAGES ***
%
%\usepackage[cmex10]{amsmath}
% A popular package from the American Mathematical Society that provides
% many useful and powerful commands for dealing with mathematics. If using
% it, be sure to load this package with the cmex10 option to ensure that
% only type 1 fonts will utilized at all point sizes. Without this option,
% it is possible that some math symbols, particularly those within
% footnotes, will be rendered in bitmap form which will result in a
% document that can not be IEEE Xplore compliant!
%
% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000
% thus preventing page breaks from occurring within multiline equations. Use:
%\interdisplaylinepenalty=2500
% after loading amsmath to restore such page breaks as IEEEtran.cls normally
% does. amsmath.sty is already installed on most LaTeX systems. The latest
% version and documentation can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/

% *** SPECIALIZED LIST PACKAGES ***
%
%\usepackage{algorithmic}
% algorithmic.sty was written by Peter Williams and Rogerio Brito.
% This package provides an algorithmic environment fo describing algorithms.
% You can use the algorithmic environment in-text or within a figure
% environment to provide for a floating algorithm. Do NOT use the algorithm
% floating environment provided by algorithm.sty (by the same authors) or
% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated
% algorithm float types and packages that provide these will not provide
% correct IEEE style captions. The latest version and documentation of
% algorithmic.sty can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/
% There is also a support site at:
% http://algorithms.berlios.de/index.html
% Also of interest may be the (relatively newer and more customizable)
% algorithmicx.sty package by Szasz Janos:
% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/

% *** ALIGNMENT PACKAGES ***
%
%\usepackage{array}
% Frank Mittelbach's and David Carlisle's array.sty patches and improves
% the standard LaTeX2e array and tabular environments to provide better
% appearance and additional user controls. As the default LaTeX2e table
% generation code is lacking to the point of almost being broken with
% respect to the quality of the end results, all users are strongly
% advised to use an enhanced (at the very least that provided by array.sty)
% set of table tools. array.sty is already installed on most systems. The
% latest version and documentation can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/required/tools/

%\usepackage{mdwmath}
%\usepackage{mdwtab}
% Also highly recommended is Mark Wooding's extremely powerful MDW tools,
% especially mdwmath.sty and mdwtab.sty which are used to format equations
% and tables, respectively. The MDWtools set is already installed on most
% LaTeX systems. The lastest version and documentation is available at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/

% IEEEtran contains the IEEEeqnarray family of commands that can be used to
% generate multiline equations as well as matrices, tables, etc., of high
% quality.

%\usepackage{eqparbox}
% Also of notable interest is Scott Pakin's eqparbox package for creating
% (automatically sized) equal width boxes - aka "natural width parboxes".
% Available at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/

% *** SUBFIGURE PACKAGES ***
%\usepackage[tight,footnotesize]{subfigure}
% subfigure.sty was written by Steven Douglas Cochran. This package makes it
% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE
% work, it is a good idea to load it with the tight package option to reduce
% the amount of white space around the subfigures. subfigure.sty is already
% installed on most LaTeX systems. The latest version and documentation can
% be obtained at:
% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/
% subfigure.sty has been superceeded by subfig.sty.

%\usepackage[caption=false]{caption}
%\usepackage[font=footnotesize]{subfig}
% subfig.sty, also written by Steven Douglas Cochran, is the modern
% replacement for subfigure.sty. However, subfig.sty requires and
% automatically loads Axel Sommerfeldt's caption.sty which will override
% IEEEtran.cls handling of captions and this will result in nonIEEE style
% figure/table captions. To prevent this problem, be sure and preload
% caption.sty with its "caption=false" package option. This is will preserve
% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later 
% (recommended due to many improvements over 1.2) of subfig.sty supports
% the caption=false option directly:
%\usepackage[caption=false,font=footnotesize]{subfig}
%
% The latest version and documentation can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/
% The latest version and documentation of caption.sty can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/

% *** FLOAT PACKAGES ***
%
%\usepackage{fixltx2e}
% fixltx2e, the successor to the earlier fix2col.sty, was written by
% Frank Mittelbach and David Carlisle. This package corrects a few problems
% in the LaTeX2e kernel, the most notable of which is that in current
% LaTeX2e releases, the ordering of single and double column floats is not
% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a
% single column figure to be placed prior to an earlier double column
% figure. The latest version and documentation can be found at:
% http://www.ctan.org/tex-archive/macros/latex/base/

%\usepackage{stfloats}
% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e
% the ability to do double column floats at the bottom of the page as well
% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in
% LaTeX2e). It also provides a command:
%\fnbelowfloat
% to enable the placement of footnotes below bottom floats (the standard
% LaTeX2e kernel puts them above bottom floats). This is an invasive package
% which rewrites many portions of the LaTeX2e float routines. It may not work
% with other packages that modify the LaTeX2e float routines. The latest
% version and documentation can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/
% Documentation is contained in the stfloats.sty comments as well as in the
% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE
% does not allow \baselineskip to stretch. Authors submitting work to the
% IEEE should note that IEEE rarely uses double column equations and
% that authors should try to avoid such use. Do not be tempted to use the
% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does
% not format its papers in such ways.

% *** PDF, URL AND HYPERLINK PACKAGES ***
%
\usepackage{url}
% url.sty was written by Donald Arseneau. It provides better support for
% handling and breaking URLs. url.sty is already installed on most LaTeX
% systems. The latest version can be obtained at:
% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/
% Read the url.sty source comments for usage information. Basically,
% \url{my_url_here}.

% *** Do not adjust lengths that control margins, column widths, etc. ***
% *** Do not use packages that alter fonts (such as pslatex).         ***
% There should be no need to do such things with IEEEtran.cls V1.6 and later.
% (Unless specifically asked to do so by the journal or conference you plan
% to submit to, of course. )

% correct bad hyphenation here
\hyphenation{op-tical net-works semi-conduc-tor}

\begin{document}
%
% paper title
% can use linebreaks \\ within to get better formatting as desired
\title{Template for Papers in Seminar Scientific Working (182.697)}

% author names and affiliations
% use a multiple column layout for up to three different
% affiliations
\author{\IEEEauthorblockN{Ulrich Schmid}
\IEEEauthorblockA{Vienna University of Technology\\
Embedded Computing Systems Group E182/2\\
Treitlstra\ss e 1-3, A-1040 Vienna (Austria)\\
Email: s@ecs.tuwien.ac.at}
\and
\IEEEauthorblockN{Andreas Steininger}
\IEEEauthorblockA{Vienna University of Technology\\
Embedded Computing Systems Group E182/2\\
Treitlstra\ss e 1-3, A-1040 Vienna (Austria)\\
Email: steininger@ecs.tuwien.ac.at}}

% conference papers do not typically use \thanks and this command
% is locked out in conference mode. If really needed, such as for
% the acknowledgment of grants, issue a \IEEEoverridecommandlockouts
% after \documentclass

% for over three affiliations, or if they all won't fit within the width
% of the page, use this alternative format:
% 
%\author{\IEEEauthorblockN{Michael Shell\IEEEauthorrefmark{1},
%Homer Simpson\IEEEauthorrefmark{2},
%James Kirk\IEEEauthorrefmark{3}, 
%Montgomery Scott\IEEEauthorrefmark{3} and
%Eldon Tyrell\IEEEauthorrefmark{4}}
%\IEEEauthorblockA{\IEEEauthorrefmark{1}School of Electrical and Computer Engineering\\
%Georgia Institute of Technology,
%Atlanta, Georgia 30332--0250\\ Email: see http://www.michaelshell.org/contact.html}
%\IEEEauthorblockA{\IEEEauthorrefmark{2}Twentieth Century Fox, Springfield, USA\\
%Email: homer@thesimpsons.com}
%\IEEEauthorblockA{\IEEEauthorrefmark{3}Starfleet Academy, San Francisco, California 96678-2391\\
%Telephone: (800) 555--1212, Fax: (888) 555--1212}
%\IEEEauthorblockA{\IEEEauthorrefmark{4}Tyrell Inc., 123 Replicant Street, Los Angeles, California 90210--4321}}

% use for special paper notices
%\IEEEspecialpapernotice{(Invited Paper)}

% make the title area
\maketitle

\begin{abstract}
%\boldmath
The abstract should concisely summarize the contents of a
paper. Since potential readers should be able to make their decision
on the personal relevance based on the abstract, the abstract should
clearly tell the reader what information he can expect to find in
the paper. The most essential issue is the problem statement and the
actual contribution of described work. The authors should always
keep in mind that the abstract is the most frequently read part of
a paper. Typically, it is just one paragraph containing, say, between
70 and 120 words.
\end{abstract}
% IEEEtran.cls defaults to using nonbold math in the Abstract.
% This preserves the distinction between vectors and scalars. However,
% if the conference you are submitting to favors bold math in the abstract,
% then you can use LaTeX's standard command \boldmath at the very start
% of the abstract to achieve this. Many IEEE journals/conferences frown on
% math in the abstract anyway.

% no keywords

% For peer review papers, you can put extra information on the cover
% page as needed:
% \ifCLASSOPTIONpeerreview
% \begin{center} \bfseries EDICS Category: 3-BBND \end{center}
% \fi
%
% For peerreview papers, this IEEEtran command inserts a page break and
% creates the second title. It will be ignored for other modes.
\IEEEpeerreviewmaketitle

\section{Introduction}

This document\footnote{This article is a rewriting/extension of 
C.~E. Salloum, W.~Elmenreich, and R.~Kirner, \emph{Template and guidelines for
  writing a scientific paper}, unpublished manuscript \cite{EEK06}. 
It has been prepared in the course of the seminar "Scientific Working" (182.697, 182.714) at TU Vienna, which shall help undergraduate students to get first experience in the art of scientific writing.} serves two purposes. First it is a template and
example for a scientific paper. Second, the text in the sections
contains useful information on structuring and writing your first
paper. We recommend to read the following sections carefully in
order to avoid common mistakes.

The introduction should consist of three parts (as paragraphs, not
to be structured into multiple headings):

The first part deals with the \emph{background} of the work and
describes the field of research. It should also elaborate on the
\emph{general problem statement} and the \emph{relevance}?

The second part should describe the focus of the paper, typically
the paragraph starts with a phrase like \zitat{The objective of this
paper is ...}.

The last part should describe the structure of the paper, for
example: The paper is structured as follows:
Section~\ref{sec:structure} explains the overall structure for
different types of scientific papers. Section~\ref{sec:writingstyle}
gives some hints on writing and covers also acronyms, figures and
tables. Section~\ref{sec:latex} gives a recommendation on {\LaTeX}
and explains how to get the necessary tools.
Section~\ref{sec:checklist} presents a checklist of common mistakes
to avoid. Section~\ref{sec:conclusion} concludes the paper.

\section{Structure of Your Paper\label{sec:structure}}

\subsection{Research Papers}

The structuring of your sections heavily depends on the \emph{type}
of your paper. For example if you have done some research
encompassing an experimental setup and measurements, your paper
could be possibly structured as follows:
\begin{itemize}
\item Abstract; Kurzfassung, Abstract
\item Introduction; Einleitung
\item Related Work; Verwandte Arbeiten
\item Basic concepts, Concepts and Terms; Grundbegriffe, Grundkonzepte und Definitionen
\item Experimental setup, Applied Method; Versuchsaufbau, Vorgangsweise
\item Results; (Experimentielle) Ergebnisse
\item Discussion, Proof; Diskussion, Beweis
\item Conclusion (and Outlook), Summary; Schlussfolgerungen, Fazit; Zusammenfassung (und Ausblick)
\item References; Literaturverzeichnis
\end{itemize}

The colons separate possible variants in naming the sections. The
variants after the semicolon give the German counterparts. If some
text is in brackets, this text could be optionally added to the
given variant (but used without brackets).

The section on related work might also appear right before the
concluding section.

The section on basic concepts should introduce the basic terms and
concepts that are needed to understand the following sections of the
paper. Sometimes, it is not necessary to have a separate section on
basic concepts, if the basic concepts are well-known or can be
covered in the introduction.

The experimental setup typically describes the used hardware,
software, and the implementation. If your implementation has a fancy
name, you could also name that section that way (for example
\emph{KHUFU System Description}.

Most papers you will read for your first paper will likely be such
\emph{research papers}.

\subsection{Survey Papers}

If you do a literature research comparing some approaches, your
paper could be possibly structured as follows:

\begin{itemize}
\item Abstract; Kurzfassung, Abstract
\item Introduction; Einleitung
\item Basic concepts, Concepts and Terms; Grundbegriffe, Grundkonzepte und Definitionen
\item Description of first approach
\item Other approach, etc. (one section per approach)
\item Comparison and Discussion
\item Conclusion, Summary; Schlussfolgerungen, Fazit; Zusammenfassung
\end{itemize}

The semantic of the list is the same as above. The comparison will
typically cover common features, differences, advantages, drawbacks.
A comparing matrix would be nice.

The paper you will write in this course will most likely be such a
\emph{survey paper}. Depending on your special topic you might
decide to split up or to combine some sections.

\section{Writing Style\label{sec:writingstyle}}

Usually you should not use the first person singular (\emph{I}) in
your text, write \emph{we} instead. As a general recommendation, use
the first person sparsely, sometimes it can be replaced by a phrase
like \emph{This work presents...}.

\subsection{Language}

If you did not make a special agreement with your mentor, you may
write your paper in English or German language. However please keep
in mind, that most literature you will have to read for your paper
will be in English language anyway.

If you use English, you might find the following hint useful: The
indefinite article \textbf{a} is used as \textbf{an} before a vowel
sound - for example \textbf{an} apple, \textbf{an} hour, \textbf{an}
unusual thing, \textbf{an} FPGA (becourse the acronym is pronouned
Ef-Pee-Gee-A), \textbf{an} HIL. Before a consonant sound represented
by a vowel letter \textbf{a} is usual -- for example \textbf{a} one,
\textbf{a} unique thing, \textbf{a} historic
chance\footnote{According to Merriam Webster, both \textbf{a} and
\textbf{an} can be used in writing before unstressed or weakly
stressed syllables with initial h, thus you could also write
\zitat{\textbf{an} historic chance}.}.

\subsection{Figures and Tables}

A figure should always be referenced and explained in the text, for
example: \emph{Figure~\ref{fig:example} shows a gear unit with three
wheels. As depicted in the figure, the second gear wheel is larger
than the other two in order to make the figure more appealing.}

% An example of a floating figure using the graphicx package.
% Note that \label must occur AFTER (or within) \caption.
% For figures, \caption should occur after the \includegraphics.
% Note that IEEEtran v1.7 and later has special internal code that
% is designed to preserve the operation of \label within \caption
% even when the captionsoff option is in effect. However, because
% of issues like this, it may be the safest practice to put all your
% \label just after \caption rather than within \caption{}.
%
% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class
% option should be used if it is desired that the figures are to be
% displayed while in draft mode.
%
%\begin{figure}[!t]
%\centering
%\includegraphics[width=2.5in]{myfigure}
% where an .eps filename suffix will be assumed under latex, 
% and a .pdf suffix will be assumed for pdflatex; or what has been declared
% via \DeclareGraphicsExtensions.
%\caption{Simulation Results}
%\label{fig_sim}
%\end{figure}

% Note that IEEE typically puts floats only at the top, even when this
% results in a large percentage of a column being occupied by floats.

% An example of a double column floating figure using two subfigures.
% (The subfig.sty package must be loaded for this to work.)
% The subfigure \label commands are set within each subfloat command, the
% \label for the overall figure must come after \caption.
% \hfil must be used as a separator to get equal spacing.
% The subfigure.sty package works much the same way, except \subfigure is
% used instead of \subfloat.
%
%\begin{figure*}[!t]
%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}%
%\label{fig_first_case}}
%\hfil
%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}%
%\label{fig_second_case}}}
%\caption{Simulation results}
%\label{fig_sim}
%\end{figure*}
%
% Note that often IEEE papers with subfigures do not employ subfigure
% captions (using the optional argument to \subfloat), but instead will
% reference/describe all of them (a), (b), etc., within the main caption.

% An example of a floating table. Note that, for IEEE style tables, the 
% \caption command should come BEFORE the table. Table text will default to
% \footnotesize as IEEE normally uses this smaller font for tables.
% The \label must come after \caption as always.
%
%\begin{table}[!t]
%% increase table row spacing, adjust to taste
%\renewcommand{\arraystretch}{1.3}
% if using array.sty, it might be a good idea to tweak the value of
% \extrarowheight as needed to properly center the text within the cells
%\caption{An Example of a Table}
%\label{table_example}
%\centering
%% Some packages, such as MDW tools, offer better commands for making tables
%% than the plain LaTeX2e tabular which is used here.
%\begin{tabular}{|c||c|}
%\hline
%One & Two\\
%\hline
%Three & Four\\
%\hline
%\end{tabular}
%\end{table}

% Note that IEEE does not put floats in the very first column - or typically
% anywhere on the first page for that matter. Also, in-text middle ("here")
% positioning is not used. Most IEEE journals/conferences use top floats
% exclusively. Note that, LaTeX2e, unlike IEEE journals/conferences, places
% footnotes above bottom floats. This can be corrected via the \fnbelowfloat
% command of the stfloats package.

\begin{figure}[ht]
\begin{center}
\includegraphics[width=.5\columnwidth]{sample_pic}
% where an .eps filename suffix will be assumed under latex, 
% and a .pdf suffix will be assumed for pdflatex; or what has been declared
% via \DeclareGraphicsExtensions.
  \caption{Example figure}
  \label{fig:example}
\end{center}
\end{figure}

\begin{table}[hbt]
\begin{center}
\begin{tabular}{|p{2cm}|p{2.5cm}|p{2cm}c@{}|}
 \hline
 Code & Element name & Size in bytes &\\
 \hline
 0 & Status & 1 &\\
 1 & Cluster name & 1 &\\
 5 & Data bytes & 4&\\
 9 & Checksum & 1&\\
 \hline
\end{tabular}
\end{center}
\caption{Table example} \label{tab:sample}
\end{table}

Tables also should always be referenced and explained in the text,
for example: \emph{Table~\ref{tab:sample} depicts the byte index for
various items. Note that the size in byte is always one except for
code 5.}

\subsection{Acronyms}

Explain acronyms at their first occurrence in the text. In order to
achieve this consistently, we recommend to use a phrase like
\emph{Very Large Scale Integration} (VLSI) to introduce the 
acronym VLSI.

\subsection{Citations and References}

Whenever you refer to previously published work, you should set a
reference to acknowledge the work you build upon. For example this
is a reference to a bachelor's thesis~\cite{Kra03}. If you
literally cite a part of someone else's work, mark the respective
sentence by quotes and italic letters and add the page number, where
its text can be found:

\zitat{An intelligent or {\em smart} transducer is the integration
of an analog or digital sensor or actuator element, a processing
unit, and a communication interface. In case of a sensor, the smart
transducer transforms the raw sensor signal to a standardized
digital representation, checks and calibrates the signal, and
transmits this digital signal to its users via a standardized
communication protocol.} \cite[p.\,175]{ES05}

Failing to explicitely mark literally cited text is a serious offense,
belonging to {\em plagiarism}.

It is also important to keep the set of published work of high quality.
For example, one problem with articles published on the Internet only
is that they are typically not reviewed.
Thus, if you want to cite sources from the Internet, you have to
{\bfseries ask your supervisor}.
In case you really cite a source from the Internet, it is important
to provide beside the url additional information about the document.
As the content of sources from the Internet tends to be unstable, it
is important to provide detailed information about the revision and
the date of access.
For example, in Wikipedia you can refer to a specific revision time
of the content: \cite{wikipedia:wcet}.

\subsection{References with Bibtex}

Bibtex is an additional program to {\LaTeX} that creates a list of
your cited references in a chapter named {\em Bibliography}. Bibtex
works with a textfile databases of references in so-called
\emph{bibfiles} (file extension \texttt{.bib}).

Regarding the (free) choice of the reference name of an entry,
we recommend to use the following convention that has proved
its value in the past: For multi-author-papers (like Fischer, 
Lynch und Paterson, 1985) use a string consisting of the first 
letter of the authors' surnames (max. 4) + year (FLP85), for
single-author papers (like Marzullo, 1987) just the first three 
letters (Mar87); if this results in several .bib entries with
the same reference name, make it unique by appending a meaningful
extension :text (like FLP85:con).

The \emph{bibfiles} contain entries of several types, the most
needed types are \texttt{book}, \texttt{inproceedings},
\texttt{article}, \texttt{techreport}, \texttt{mastersthesis}, and
\texttt{phdthesis}. Table~\ref{table:bibtextemplates} lists templates
for these types, whereas each asterisk (*) should be replaced by the
respective data, if this data is not available, the whole line
should be removed. The case of the element names does not matter to
Bibtex, however in the examples we have used UPPERCASE for the
obligatory fields and lowercase for the optional fields. To see some
examples, have a look into the file \texttt{bibfile.bib}. For more
information, read~\cite{Pat88}.

\begin{table}
\newcommand{\mybibtabwidth}{0.45\columnwidth}
{\scriptsize
\begin{tabular}{ll}
  \begin{minipage}{\mybibtabwidth}
  \begin{verbatim}
@BOOK{*,
  AUTHOR =       {*},
  editor =       {*},
  TITLE =        {*},
  PUBLISHER =    {*},
  YEAR =         {*},
  volume =       {*},
  number =       {*},
  series =       {*},
  address =      {*},
  edition =      {*},
  month =        {*},
  note =         {*}
}

@ARTICLE{*,
  AUTHOR =       {*},
  TITLE =        {*},
  JOURNAL =      {*},
  YEAR =         {*},
  volume =       {*},
  number =       {*},
  pages =        {*},
  month =        {*},
  note =         {*}
}

@TECHREPORT{*,
  AUTHOR =       {*},
  TITLE =        {*},
  INSTITUTION =  {*},
  YEAR =         {*},
  type =         {*},
  number =       {*},
  address =      {*},
  month =        {*},
  note =         {*}
}
  \end{verbatim}
  \end{minipage} &

  \begin{minipage}{\mybibtabwidth}
  \begin{verbatim}
@INPROCEEDINGS{*,
  AUTHOR =       {*},
  TITLE =        {*},
  BOOKTITLE =    {*},
  YEAR =         {*},
  editor =       {*},
  volume =       {*},
  number =       {*},
  series =       {*},
  pages =        {*},
  address =      {*},
  month =        {*},
  organization = {*},
  publisher =    {*},
  note =         {*}
}

@MASTERSTHESIS{*,
  AUTHOR =       {*},
  TITLE =        {*},
  SCHOOL =       {*},
  YEAR =         {*},
  type =         {*},
  address =      {*},
  month =        {*},
  note =         {*}
}

@PHDTHESIS{*,
  AUTHOR =       {*},
  TITLE =        {*},
  SCHOOL =       {*},
  YEAR =         {*},
  type =         {*},
  address =      {*},
  month =        {*},
  note =         {*}
}
  \end{verbatim}
  \end{minipage} \\
  \end{tabular}
}
\caption{Common Bibtex templates}
\label{table:bibtextemplates}
\end{table}

\section{Using {\LaTeX} for writing your paper\label{sec:latex}}

{\LaTeX} is a type-setting system commonly used in scientific
publishing. Together with the tool BibteX it supports you in writing
proper articles with correctly formatted citations. We recommend
also to use {\LaTeX} for your paper. {\LaTeX} and most tools are
freely available.

This template can be compiled with the \texttt{latex} command or the
\texttt{pdflatex} command. While \texttt{latex} creates an
intermediate file format (.dvi) that can be further processed into a
\texttt{.ps} or \texttt{.pdf} file, the \texttt{pdflatex} command
directly creates a \texttt{.pdf} file.

Note that with \texttt{latex} the \verb+\includegraphics+ accepts
only .eps files, while with \texttt{pdflatex} accepts \texttt{.pdf},
\texttt{.png}, or \texttt{.jpg}. Luckily, the file extension can be
omitted in order that \verb+\includegraphics{pics/example}+ will
look for file with name \texttt{example.eps} in \texttt{latex} mode
and for a file with name \texttt{example.pdf}, \texttt{example.png},
or \texttt{example.jpg} in \texttt{pdflatex} mode. If you already
have an \texttt{.eps} file, you may create a respective
\texttt{.pdf} file with the commandline conversion tool
\texttt{epstopdf}.

\subsection{{\LaTeX} Tutorials}

We will not give an introduction to {\LaTeX} here, since there exist
already a number of fine introductions into the subject.

A good concise introduction is given by~\cite{OPHS05}.

\subsection{Recommended {\LaTeX} Software for Windows}

We recommend MikTeX, which is a an up-to-date implementation of
{\TeX} and {\LaTeX} for all current variants of Windows on x86
systems. MikTeX is freely available at \url{http://www.miktex.org}.

As an editor, we recommend the free \emph{TeXnicCenter} (available
at \url{http://www.toolscenter.org}). Both, MikTeX and TeXnicCenter
are published under the GPL. \emph{TeXnicCenter} comes with an
integrated spell checker, otherwise you are recommended to install
the Windows version of \emph{aspell}, an open source spell checker
under the GPL is available at \url{http://aspell.net/win32/}.

Alternatively, you can use Cygwin, which provides you a Unix-like working
environment for Windows. Cygwin is freely available under the GPL
at \url{http://www.cygwin.com}.
Cygwin also allows you to use the software packages described in
Section~\ref{sec_sw_linux_bsd}.

\subsection{Recommended {\LaTeX} Software for Linux and BSDs}
\label{sec_sw_linux_bsd}

The standard distributions for Linux already come with a {\LaTeX}
system (typically \texttt{tetex}).

As an editor, we recommend the Kile editor (available at
\url{http://kile.sourceforge.net/} under GPL). As spell checker
we recommend \emph{aspell}, an open source spell checker that
replaces the older \emph{ispell} checker. \emph{aspell} is included
in most distributions, otherwise it can be downloaded from
\url{http://www.gnu.org/software/aspell/}.

\subsection{Recommended {\LaTeX} Software for Apple Mac OS X}

The \emph{darwin ports} (\url{http://darwinports.opendarwin.org/})
provide a port of \emph{teTeX} that can be installed under Apple Mac
OS X.

As an editor, we recommend TeXShop (available at
\url{http://www.uoregon.edu/~koch/texshop/} under GPL). As
spell and grammar checker we recommend Excalibur
(\url{http://www.eg.bucknell.edu/~excalibr/}).

\section{Common Mistakes to Avoid\label{sec:checklist}}

The following checklist should help in avoiding some frequently made
mistakes, if any of the following propositions apply for your paper,
there is a problem:

\begin{itemize}

\item Your abstract has a heading enummeration

\item You have citations in your abstract

\item The introduction does not cover the three parts as described above

\item The introduction contains subheadings

\item You refer to chapters instead of sections (chapters is only for books or theses)

\item You described different aspects than promised in the title. For example your paper is on modular robotics and you elaborate on robot control.

\item You described different aspects for the compared approaches. For example you elaborate on communication speed for system A, then you write about the code size of system B (better: describe both aspects for all three systems)

\item You copied some parts of the text from other work without proper referencing and citing

\item You used automatic translation tools to produce text by translating it from another language

\item Your paper contains many typos and grammatical errors (Use an electronic spellchecker. Please!)

\item You work in a team and did not spend time for reading and integrating the parts of the teammembers.

\item You used color in your figures and refer to the ``blue'' line (assume that your readers use a monochrome printer)

\item You mainly used websites and other unrefereed material as your sources

\item You cite some in your conclusion which you have not mentioned before

\item Some forenames in the references are abbreviated, some not

\item Some references miss a publishing date

\end{itemize}

\section{Conclusion}
\label{sec:conclusion}

The conclusion should briefly summarize the problem statement and
the general content of the work and the emphasize on the main
contribution of the work.

When writing the conclusion keep in mind that some readers may not
have gone through the whole paper, but have jumped directly to the
conclusion after having read the abstract in order the decide on the
personal relevance of the paper. Therefore, the conclusion should be
self-contained, which means that a reader should be able to
understand the essence of the conclusion without having to read the
whole paper.

The conclusion typically ends with an outlook that describes
possible extensions of the presented approaches and of planned
future work.

% conference papers do not normally have an appendix

% use section* for acknowledgement
\section*{Acknowledgment}

This template has been adapted from the template \cite{EEK06} written for the
Proseminar GMA in 2006 by Christian El Salloum, Wilfried Elmenreich, 
and Raimund Kirner. The authors are much indebted to our colleagues
for their great work.

% trigger a \newpage just before the given reference
% number - used to balance the columns on the last page
% adjust value as needed - may need to be readjusted if
% the document is modified later
%\IEEEtriggeratref{8}
% The "triggered" command can be changed if desired:
%\IEEEtriggercmd{\enlargethispage{-5in}}

% references section

% can use a bibliography generated by BibTeX as a .bbl file
% BibTeX documentation can be easily obtained at:
% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/
% The IEEEtran BibTeX style support page is at:
% http://www.michaelshell.org/tex/ieeetran/bibtex/
\bibliographystyle{IEEEtran}
% argument is your BibTeX string definitions and bibliography database(s)
\bibliography{bibfile}
%
% <OR> manually copy in the resultant .bbl file
% set second argument of \begin to the number of references
% (used to reserve space for the reference number labels box)
%\begin{thebibliography}{1}

%\bibitem{IEEEhowto:kopka}
%H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus
%  0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999.

%\end{thebibliography}

% that's all folks
\end{document}
